Welcome to ‘What are Microservices?’ After watching this video, you will be able to describe what microservices are, explain the benefits of
microservices architecture, and explain how microservices can be scaled. Microservices architecture is an approach
in which a single application is composed of many loosely coupled and independently deployable smaller services. These services typically have their own technology stack, inclusive
of the database and data management model. Teams can even choose different
programming languages for different components as they are dependent
on each other via an API endpoint. Microservices components communicate with
one another over a combination of REST APIs, event streaming, and message brokers, and they are segregated and
organized by business functionality, with the line separating services
referred to as a bounded context. Since there is no interdependency between
services, you can update code more easily to add new features or functionality
without touching the entire application. Each team can choose its own technology stack which suits its needs and expertise to build
components for which the team is responsible. And these components can be scaled independently of one another,
reducing the waste and cost associated with having to scale entire applications because
a single feature might be facing too much load. So, wherever you see scaling of microservices,
it usually involves horizontal scaling. Horizontal scaling means scaling by
adding more instances of resources, also described as “scaling out”. With microservices, individual services
can be individually deployed and scaled. Done correctly, microservices
require less infrastructure because they enable precise scaling of
only the components that require it, instead of the entire application in
the case of monolithic applications. An API call is often an effective way of initially
establishing the state for a given service. However, it’s not a particularly effective
way of staying up to date on progress. This is where event streaming can
help broadcast the state change, which helps in scaling the microservice
by introducing this message broker. In this video, you learned that: Microservices make each application
component its own service, and each service communicates via an API, microservices allow application components
to use different technology stacks, microservices enable individual
components to scale in response to demand, microservices lessen risks associated with change
because components can iterate independently, and failures in one service do not
necessarily impact other services.